\chapter{Future Work}
In its current state, the product is not usable. Although large parts of the interface have been implemented, it still lacks crucial and necessary functions. The design and the code of the program can be greatly improved to provide better results.

One major future consideration is that the design of the tests could have been optimized. One of them being the feedback of the participants following the test. No post-interviews nor surveys were conducted to objectively investigate and gather data through feedback of what could have been issues in the test, as well as the general user experience of using the project application.  

Another aspect of the development that could be improved upon, and potentially help improve the experience, would be to implement even more help to the examples of the different effects. This could be done with a short written or oral explanation of the effects, which could help further the user's understanding of what exactly the effect does to the signal. Such information, together with the auditory and visual clues given, could possibly give an even better result in the end.

In its final stage, the product should be usable by both students and teachers. The students should be able to bring it to class, and quickly and easily be able to check up on an effect and get an overview of that effect. Likewise, the teacher could bring up the program during class to show the effects live, and at the same time give an explanation of the effect, to make sure that everyone understood the topic that he was teaching.

When the product is completely done, extra features could be added; for example being able to make one of the visualization windows go into full screen, so that it would be easier for the teacher to show the visualizers to the class.

Looking at the code, it is worth reconsidering how to actually implement it. It would be important to determine whether or not to continue with the libraries currently used, and even to continue with the programming language currently used. It might be worth looking for more powerful libraries, which might make the implementation easier. Also, it could be argued that Java isn't the most suited language for this. Maybe C or C++ would have been a better choice, performance-wise. These are ideal candidates that many professionals within the audio processing industry recommends more low-level languages \cite{lance}.

A broad user-centered design test would be desired to determine a more suitable interface to accommodate the target group better. The test would require to focus on both the usability of the program - whether it really does what was intended for - and a user experience test, to see if the feelings evoked in the users are the ones as intended or not. These tests should be done regularly as to always ensure the design of the program was properly guided towards the target group.

Furthermore, with the help of other fields of science, these tests could help us understand where the thresholds information overload, so as to not bombard the user with an unnecessarily large amount of information. It might be outside of the field of Medialogy, but it is definitely something worth exploring more. One way would be to join up with other educations to learn more about the cognitive elements involved in developing a program like this. The same goes for learning styles. In future work, it would be an interesting topic to explore further.